NetNews Offline 2/NetNews Offline Volume 2.iso/news/comp/lang/c-part1/5428

Text File | 1996-08-05 | 1.6 KB | 43 lines

Path: mail2news.demon.co.uk!genesis.demon.co.uk
From: Lawrence Kirby <[e-mail]>
Newsgroups: comp.lang.c
Subject: Re: Borland C - compiler not finding window.h file.
Date: Fri, 09 Feb 96 15:36:38 GMT
Organization: none
Message-ID: <[e-mail]>
References: <4f85f9$[e-mail]> <[e-mail]>
Reply-To: [e-mail]
X-NNTP-Posting-Host: genesis.demon.co.uk
X-Newsreader: Demon Internet Simple News v1.27
X-Mail2News-Path: genesis.demon.co.uk

In article <[e-mail]>
           [e-mail] "Norman Bullen" writes:

>Do you have <...> or "..." surrounding the include file name? <...> will
>find the file in any of the directories specified in the IDE for include
>files; "..." will only find the file in the current directory or a fully
>qualified directory.

Not if it is an ANSI comforming implementation.  What:

#include "stdio.h"

will search is implementation defined (but it will often include the
curent directory). However if that search fails to find anything it will
proceed to perform the same search as:

#include <stdio.h>

so if the <> form finds something then the "" form is guaranteed to find
something as well (although not necessarily the same thing). Nevertheless
<> should be used for standard/system header files to prevent the system
finding the wrong file (e.g. if there happens to be a file called
stdio.h in the current directory).

--
-----------------------------------------
Lawrence Kirby | [e-mail]
Wilts, England | [e-mail]
-----------------------------------------